<html><head><title>RFC2621</title>
<link rel='shortcut icon' href='/favicon.ico' type='image/x-icon'>
<meta name='description' content='RFC2621'>
<meta name='aesop' content='information'>
</head>
<body bgcolor="#ffffff">
<div align="center">
<H1><FONT FACE="arial, sans-serif, helvetica">RFC2621</FONT></H1><BR>
<a href="http://RFC.net/rfc-index.html">RFC index</a> | <a href="http://RFC.net/std-index.html">STD index</a> | <a href="http://RFC.net/bcp-index.html">BCP index</a> | <a href="http://RFC.net/fyi-index.html">FYI index</a><br>
<A HREF="/rfc2621.txt">Plain text</A> | <A HREF="/rfc2621.txt.gz">gzipped plain text</A> | <A HREF="rfc2621.ps">A4 postscript</A> | <A HREF="rfc2621.2up.ps">A4 postscript, 2 up</A> | <A HREF="rfc2621.4up.ps">A4 postscript, 4 up</A><BR>
</DIV>
<pre>
<A NAME="p1"></A>






Network Working Group                                             G. Zorn
Request for Comments: 2621                                       B. Aboba
Category: Informational                                         Microsoft
                                                                June 1999


                      RADIUS Accounting Server MIB

Status of this Memo

   This memo provides information for the Internet community.  This memo
   does not specify an Internet standard of any kind.  Distribution of
   this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (1999).  All Rights Reserved.

Abstract

   This memo defines a set of extensions which instrument RADIUS
   accounting server functions. These extensions represent a portion of
   the Management Information Base (MIB) for use with network management
   protocols in the Internet community.  Using these extensions IP-based
   management stations can manage RADIUS accounting servers.

<h2><a name='s1.'>1.  Introduction</a></h2>

   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in the Internet community.
   In particular, it describes managed objects used for managing RADIUS
   accounting servers.

   RADIUS accounting servers are today widely deployed by dialup
   Internet Service Providers, in order to provide accounting services.
   As a result, the effective management of RADIUS accounting servers is
   of considerable importance.

<h2><a name='s2.'>2.  The SNMP Management Framework</a></h2>

   The SNMP Management Framework presently consists of five major
   components:

    o   An overall architecture, described in <A HREF="http://RFC.net/rfc2571.html">RFC 2571</A> [1].

    o   Mechanisms for describing and naming objects and events for the
        purpose of management. The first version of this Structure of
        Management Information (SMI) is called SMIv1 and described in



Zorn &amp; Aboba                 Informational                      [Page 1]
<hr><a name='p2'></a>

<A HREF="http://RFC.net/rfc2621.html">RFC 2621</A>              RADIUS Accounting Server MIB             June 1999


        <A HREF="http://RFC.net/std15.html">STD 15</A>, <A HREF="http://RFC.net/rfc1155.html">RFC 1155</A> [2], <A HREF="http://RFC.net/std16.html">STD 16</A>, <A HREF="http://RFC.net/rfc1212.html">RFC 1212</A> [3] and <A HREF="http://RFC.net/rfc1215.html">RFC 1215</A> [4].
        The second version, called SMIv2, is described in <A HREF="http://RFC.net/std58.html">STD 58</A>, RFC
        2578 [5], <A HREF="http://RFC.net/rfc2579.html">RFC 2579</A> [6] and <A HREF="http://RFC.net/rfc2580.html">RFC 2580</A> [7].

    o   Message protocols for transferring management information. The
        first version of the SNMP message protocol is called SNMPv1 and
        described in <A HREF="http://RFC.net/std15.html">STD 15</A>, <A HREF="http://RFC.net/rfc1157.html">RFC 1157</A> [8]. A second version of the
        SNMP message protocol, which is not an Internet standards
        track protocol, is called SNMPv2c and described in <A HREF="http://RFC.net/rfc1901.html">RFC 1901</A>
        [9] and <A HREF="http://RFC.net/rfc1906.html">RFC 1906</A> [10].  The third version of the message
        protocol is called SNMPv3 and described in <A HREF="http://RFC.net/rfc1906.html">RFC 1906</A> [10], RFC
        2572 [11] and <A HREF="http://RFC.net/rfc2574.html">RFC 2574</A> [12].

    o   Protocol operations for accessing management information. The
        first set of protocol operations and associated PDU formats is
        described in <A HREF="http://RFC.net/std15.html">STD 15</A>, <A HREF="http://RFC.net/rfc1157.html">RFC 1157</A> [8]. A second set of protocol
        operations and associated PDU formats is described in <A HREF="http://RFC.net/rfc1905.html">RFC 1905</A>
        [13].

    o   A set of fundamental applications described in <A HREF="http://RFC.net/rfc2573.html">RFC 2573</A> [14] and
        the view-based access control mechanism described in <A HREF="http://RFC.net/rfc2575.html">RFC 2575</A>
        [15].

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  Objects in the MIB are
   defined using the mechanisms defined in the SMI.

   This memo specifies a MIB module that is compliant to the SMIv2. A
   MIB conforming to the SMIv1 can be produced through the appropriate
   translations. The resulting translated MIB must be semantically
   equivalent, except where objects or events are omitted because no
   translation is possible (use of Counter64). Some machine readable
   information in SMIv2 will be converted into textual descriptions in
   SMIv1 during the translation process. However, this loss of machine
   readable information is not considered to change the semantics of the
   MIB.

<h2><a name='s3.'>3.  Overview</a></h2>

   The RADIUS accounting protocol, described in [16], distinguishes
   between the client function and the server function. In RADIUS
   accounting, clients send Accounting-Requests, and servers reply with
   Accounting-Responses.  Typically NAS devices implement the client
   function, and thus would be expected to implement the RADIUS
   accounting client MIB, while RADIUS accounting servers implement the
   server function, and thus would be expected to implement the RADIUS
   accounting server MIB.




Zorn &amp; Aboba                 Informational                      [Page 2]
<hr><a name='p3'></a>

<A HREF="http://RFC.net/rfc2621.html">RFC 2621</A>              RADIUS Accounting Server MIB             June 1999


   However, it is possible for a RADIUS accounting entity to perform
   both client and server functions. For example, a RADIUS proxy may act
   as a server to one or more RADIUS accounting clients, while
   simultaneously acting as an accounting client to one or more
   accounting servers.  In such situations, it is expected that RADIUS
   entities combining client and server functionality will support both
   the client and server MIBs.

<h2><a name='s3.1.'>3.1.  Selected objects</a></h2>

   This MIB module contains thirteen scalars as well as a single table:

   (1)  the RADIUS Accounting Client Table contains one row for each
        RADIUS accounting client that the server shares a secret with.

   Each entry in the RADIUS Accounting Client Table includes eleven
   columns presenting a view of the activity of the RADIUS accounting
   server.

<h2><a name='s4.'>4.  Definitions</a></h2>

RADIUS-ACC-SERVER-MIB DEFINITIONS ::= BEGIN

IMPORTS
       MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY,
       Counter32, Integer32,
       IpAddress, TimeTicks, mib-2      FROM SNMPv2-SMI
       SnmpAdminString                  FROM SNMP-FRAMEWORK-MIB
       MODULE-COMPLIANCE, OBJECT-GROUP  FROM SNMPv2-CONF;

radiusAccServMIB MODULE-IDENTITY
       LAST-UPDATED &quot;9906110000Z&quot; -- 11 Jun 1999
       ORGANIZATION &quot;IETF RADIUS Working Group.&quot;
       CONTACT-INFO
          &quot; Bernard Aboba
            Microsoft
            One Microsoft Way
            Redmond, WA  98052
            US

            Phone: +1 425 936 6605
            EMail: bernarda@microsoft.com&quot;
       DESCRIPTION
           &quot;The MIB module for entities implementing the server
            side of the Remote Access Dialin User Service (RADIUS)
            accounting protocol.&quot;
       REVISION &quot;9906110000Z&quot;    -- 11 Jun 1999
       DESCRIPTION &quot;Initial version as published in <A HREF="http://RFC.net/rfc2621.html">RFC 2621</A>&quot;



Zorn &amp; Aboba                 Informational                      [Page 3]
<hr><a name='p4'></a>

<A HREF="http://RFC.net/rfc2621.html">RFC 2621</A>              RADIUS Accounting Server MIB             June 1999


       ::= { radiusAccounting 1 }

radiusMIB OBJECT-IDENTITY
       STATUS  current
       DESCRIPTION
           &quot;The OID assigned to RADIUS MIB work by the IANA.&quot;
        ::= { mib-2 67 }

radiusAccounting  OBJECT IDENTIFIER ::= {radiusMIB 2}

radiusAccServMIBObjects     OBJECT IDENTIFIER ::=
                                                { radiusAccServMIB 1 }

radiusAccServ      OBJECT IDENTIFIER ::= { radiusAccServMIBObjects 1 }

radiusAccServIdent OBJECT-TYPE
       SYNTAX      SnmpAdminString
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
             &quot;The implementation identification string for the
              RADIUS accounting server software in use on the
              system, for example; `FNS-2.1'&quot;
       ::= {radiusAccServ 1}

radiusAccServUpTime OBJECT-TYPE
       SYNTAX      TimeTicks
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
             &quot;If the server has a persistent state (e.g., a process),
              this value will be the time elapsed (in hundredths of a
              second) since the server process was started.
              For software without persistent state, this value will
              be zero.&quot;
       ::= {radiusAccServ 2}

radiusAccServResetTime OBJECT-TYPE
       SYNTAX      TimeTicks
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
             &quot;If the server has a persistent state (e.g., a process)
              and supports a `reset' operation (e.g., can be told to
              re-read configuration files), this value will be the
              time elapsed (in hundredths of a second) since the
              server was `reset.'  For software that does not
              have persistence or does not support a `reset' operation,



Zorn &amp; Aboba                 Informational                      [Page 4]
<hr><a name='p5'></a>

<A HREF="http://RFC.net/rfc2621.html">RFC 2621</A>              RADIUS Accounting Server MIB             June 1999


              this value will be zero.&quot;
       ::= {radiusAccServ 3}

radiusAccServConfigReset OBJECT-TYPE
       SYNTAX INTEGER { other(1),
                        reset(2),
                        initializing(3),
                        running(4)}
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION
              &quot;Status/action object to reinitialize any persistent
               server state.  When set to reset(2), any persistent
               server state (such as a process) is reinitialized as if
               the server had just been started.  This value will
               never be returned by a read operation.  When read, one
               of the following values will be returned:
                   other(1) - server in some unknown state;
                   initializing(3) - server (re)initializing;
                   running(4) - server currently running.&quot;
       ::= {radiusAccServ 4}

-- New Stats proposed by Dale E. Reed Jr (daler@iea.com)

radiusAccServTotalRequests OBJECT-TYPE
       SYNTAX Counter32
       MAX-ACCESS read-only
       STATUS current
       DESCRIPTION
             &quot;The number of packets received on the
              accounting port.&quot;
       ::= { radiusAccServ 5 }

radiusAccServTotalInvalidRequests OBJECT-TYPE
       SYNTAX Counter32
       MAX-ACCESS read-only
       STATUS current
       DESCRIPTION
             &quot;The number of RADIUS Accounting-Request packets
              received from unknown addresses.&quot;
       ::= { radiusAccServ 6 }

radiusAccServTotalDupRequests OBJECT-TYPE
       SYNTAX Counter32
       MAX-ACCESS read-only
       STATUS current
       DESCRIPTION
             &quot;The number of duplicate RADIUS Accounting-Request



Zorn &amp; Aboba                 Informational                      [Page 5]
<hr><a name='p6'></a>

<A HREF="http://RFC.net/rfc2621.html">RFC 2621</A>              RADIUS Accounting Server MIB             June 1999


              packets received.&quot;
       ::= { radiusAccServ 7 }

radiusAccServTotalResponses OBJECT-TYPE
       SYNTAX Counter32
       MAX-ACCESS read-only
       STATUS current
       DESCRIPTION
             &quot;The number of RADIUS Accounting-Response packets sent.&quot;
       ::= { radiusAccServ 8 }

radiusAccServTotalMalformedRequests OBJECT-TYPE
       SYNTAX Counter32
       MAX-ACCESS read-only
       STATUS current
       DESCRIPTION
             &quot;The number of malformed RADIUS Accounting-Request
              packets received. Bad authenticators or unknown
              types are not included as malformed Access-Requests.&quot;
       ::= { radiusAccServ 9 }

radiusAccServTotalBadAuthenticators OBJECT-TYPE
      SYNTAX Counter32
      MAX-ACCESS read-only
      STATUS current
      DESCRIPTION
            &quot;The number of RADIUS Accounting-Request packets
             which contained invalid Signature attributes.&quot;
      ::= { radiusAccServ 10 }

radiusAccServTotalPacketsDropped OBJECT-TYPE
      SYNTAX Counter32
      MAX-ACCESS read-only
      STATUS current
      DESCRIPTION
            &quot;The number of incoming packets silently discarded
             for a reason other than malformed, bad authenticators,
             or unknown types.&quot;
      ::= { radiusAccServ 11 }

radiusAccServTotalNoRecords OBJECT-TYPE
       SYNTAX Counter32
       MAX-ACCESS read-only
       STATUS current
       DESCRIPTION
             &quot;The number of RADIUS Accounting-Request packets
              which were received and responded to but not
              recorded.&quot;



Zorn &amp; Aboba                 Informational                      [Page 6]
<hr><a name='p7'></a>

<A HREF="http://RFC.net/rfc2621.html">RFC 2621</A>              RADIUS Accounting Server MIB             June 1999


       ::= { radiusAccServ 12 }

radiusAccServTotalUnknownTypes OBJECT-TYPE
      SYNTAX Counter32
      MAX-ACCESS read-only
      STATUS current
      DESCRIPTION
            &quot;The number of RADIUS packets of unknowntype which
             were received.&quot;
      ::= { radiusAccServ 13 }

-- End of new

radiusAccClientTable OBJECT-TYPE
       SYNTAX     SEQUENCE OF RadiusAccClientEntry
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
             &quot;The (conceptual) table listing the RADIUS accounting
              clients with which the server shares a secret.&quot;
       ::= { radiusAccServ 14 }

radiusAccClientEntry OBJECT-TYPE
       SYNTAX     RadiusAccClientEntry
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
             &quot;An entry (conceptual row) representing a RADIUS
              accounting client with which the server shares a secret.&quot;
       INDEX      { radiusAccClientIndex }
       ::= { radiusAccClientTable 1 }

RadiusAccClientEntry ::= SEQUENCE {
       radiusAccClientIndex                           Integer32,
       radiusAccClientAddress                         IpAddress,
       radiusAccClientID                        SnmpAdminString,
       radiusAccServPacketsDropped                    Counter32,
       radiusAccServRequests                          Counter32,
       radiusAccServDupRequests                       Counter32,
       radiusAccServResponses                         Counter32,
       radiusAccServBadAuthenticators                 Counter32,
       radiusAccServMalformedRequests                 Counter32,
       radiusAccServNoRecords                         Counter32,
       radiusAccServUnknownTypes                      Counter32
}

radiusAccClientIndex OBJECT-TYPE
       SYNTAX     Integer32 (1..2147483647)



Zorn &amp; Aboba                 Informational                      [Page 7]
<hr><a name='p8'></a>

<A HREF="http://RFC.net/rfc2621.html">RFC 2621</A>              RADIUS Accounting Server MIB             June 1999


       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
             &quot;A number uniquely identifying each RADIUS accounting
              client with which this server communicates.&quot;
       ::= { radiusAccClientEntry 1 }

radiusAccClientAddress OBJECT-TYPE
       SYNTAX     IpAddress
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
             &quot;The NAS-IP-Address of the RADIUS accounting client
              referred to in this table entry.&quot;
       ::= { radiusAccClientEntry 2 }

radiusAccClientID OBJECT-TYPE
       SYNTAX     SnmpAdminString
       MAX-ACCESS read-only
       STATUS     current
       DESCRIPTION
             &quot;The NAS-Identifier of the RADIUS accounting client
              referred to in this table entry. This is not necessarily
              the same as sysName in MIB II.&quot;
       ::= { radiusAccClientEntry 3 }

-- Server Counters
--
-- Requests - DupRequests - BadAuthenticators - MalformedRequests -
-- UnknownTypes -  PacketsDropped - Responses = Pending
--
-- Requests - DupRequests - BadAuthenticators - MalformedRequests -
-- UnknownTypes - PacketsDropped - NoRecords = entries logged

radiusAccServPacketsDropped OBJECT-TYPE
      SYNTAX Counter32
      MAX-ACCESS read-only
      STATUS current
      DESCRIPTION
           &quot;The number of incoming packets received
            from this client and silently discarded
            for a reason other than malformed, bad
            authenticators, or unknown types.&quot;
     ::= { radiusAccClientEntry  4 }

radiusAccServRequests OBJECT-TYPE
       SYNTAX Counter32
       MAX-ACCESS read-only



Zorn &amp; Aboba                 Informational                      [Page 8]
<hr><a name='p9'></a>

<A HREF="http://RFC.net/rfc2621.html">RFC 2621</A>              RADIUS Accounting Server MIB             June 1999


       STATUS current
       DESCRIPTION
             &quot;The number of packets received from this
              client on the accounting port.&quot;
       ::= { radiusAccClientEntry  5 }

radiusAccServDupRequests OBJECT-TYPE
       SYNTAX Counter32
       MAX-ACCESS read-only
       STATUS current
       DESCRIPTION
             &quot;The number of duplicate RADIUS Accounting-Request
              packets received from this client.&quot;
       ::= { radiusAccClientEntry 6 }

radiusAccServResponses OBJECT-TYPE
       SYNTAX Counter32
       MAX-ACCESS read-only
       STATUS current
       DESCRIPTION
             &quot;The number of RADIUS Accounting-Response packets
              sent to this client.&quot;
       ::= { radiusAccClientEntry  7 }

radiusAccServBadAuthenticators OBJECT-TYPE
       SYNTAX Counter32
       MAX-ACCESS read-only
       STATUS current
       DESCRIPTION
             &quot;The number of RADIUS Accounting-Request packets
              which contained invalid  authenticators received
              from this client.&quot;
       ::= { radiusAccClientEntry  8 }

radiusAccServMalformedRequests OBJECT-TYPE
       SYNTAX Counter32
       MAX-ACCESS read-only
       STATUS current
       DESCRIPTION
             &quot;The number of malformed RADIUS Accounting-Request
              packets which were received from this client.
              Bad authenticators and unknown types
              are not included as malformed Accounting-Requests.&quot;
       ::= { radiusAccClientEntry  9 }

radiusAccServNoRecords OBJECT-TYPE
       SYNTAX Counter32
       MAX-ACCESS read-only



Zorn &amp; Aboba                 Informational                      [Page 9]
<hr><a name='p10'></a>

<A HREF="http://RFC.net/rfc2621.html">RFC 2621</A>              RADIUS Accounting Server MIB             June 1999


       STATUS current
       DESCRIPTION
             &quot;The number of RADIUS Accounting-Request packets
              which were received and responded to but not
              recorded.&quot;
       ::= { radiusAccClientEntry  10 }

radiusAccServUnknownTypes OBJECT-TYPE
       SYNTAX Counter32
       MAX-ACCESS read-only
       STATUS current
       DESCRIPTION
             &quot;The number of RADIUS packets of unknown type which
              were received from this client.&quot;
       ::= { radiusAccClientEntry  11 }


-- conformance information

radiusAccServMIBConformance
              OBJECT IDENTIFIER ::= { radiusAccServMIB 2 }
radiusAccServMIBCompliances
              OBJECT IDENTIFIER ::= { radiusAccServMIBConformance 1 }
radiusAccServMIBGroups
              OBJECT IDENTIFIER ::= { radiusAccServMIBConformance 2 }

-- compliance statements

radiusAccServMIBCompliance MODULE-COMPLIANCE
       STATUS  current
       DESCRIPTION
             &quot;The compliance statement for accounting servers
              implementing the RADIUS Accounting Server MIB.&quot;
       MODULE  -- this module
       MANDATORY-GROUPS { radiusAccServMIBGroup }

       OBJECT        radiusAccServConfigReset
       WRITE-SYNTAX  INTEGER { reset(2) }
       DESCRIPTION  &quot;The only SETable value is 'reset' (2).&quot;

       ::= { radiusAccServMIBCompliances 1 }


-- units of conformance

radiusAccServMIBGroup OBJECT-GROUP
      OBJECTS {radiusAccServIdent,
               radiusAccServUpTime,



Zorn &amp; Aboba                 Informational                     [Page 10]
<hr><a name='p11'></a>

<A HREF="http://RFC.net/rfc2621.html">RFC 2621</A>              RADIUS Accounting Server MIB             June 1999


               radiusAccServResetTime,
               radiusAccServConfigReset,
               radiusAccServTotalRequests,
               radiusAccServTotalInvalidRequests,
               radiusAccServTotalDupRequests,
               radiusAccServTotalResponses,
               radiusAccServTotalMalformedRequests,
               radiusAccServTotalBadAuthenticators,
               radiusAccServTotalPacketsDropped,
               radiusAccServTotalNoRecords,
               radiusAccServTotalUnknownTypes,
               radiusAccClientAddress,
               radiusAccClientID,
               radiusAccServPacketsDropped,
               radiusAccServRequests,
               radiusAccServDupRequests,
               radiusAccServResponses,
               radiusAccServBadAuthenticators,
               radiusAccServMalformedRequests,
               radiusAccServNoRecords,
               radiusAccServUnknownTypes
              }
      STATUS  current
      DESCRIPTION
            &quot;The collection of objects providing management of
             a RADIUS Accounting Server.&quot;
      ::= { radiusAccServMIBGroups 1 }

END

<h2><a name='s5.'>5.  References</a></h2>

   [1]  Harrington, D., Presuhn, R., and B. Wijnen, &quot;An Architecture
        for Describing SNMP Management Frameworks&quot;, <A HREF="http://RFC.net/rfc2571.html">RFC 2571</A>, April
        1999.

   [2]  Rose, M., and K. McCloghrie, &quot;Structure and Identification of
        Management Information for TCP/IP-based Internets&quot;, <A HREF="http://RFC.net/std16.html">STD 16</A>, RFC
        1155, May 1990.

   [3]  Rose, M., and K. McCloghrie, &quot;Concise MIB Definitions&quot;, <A HREF="http://RFC.net/std16.html">STD 16</A>,
        <A HREF="http://RFC.net/rfc1212.html">RFC 1212</A>, March 1991.

   [4]  Rose, M., &quot;A Convention for Defining Traps for use with the
        SNMP&quot;, <A HREF="http://RFC.net/rfc1215.html">RFC 1215</A>, Performance Systems International, March 1991.






Zorn &amp; Aboba                 Informational                     [Page 11]
<hr><a name='p12'></a>

<A HREF="http://RFC.net/rfc2621.html">RFC 2621</A>              RADIUS Accounting Server MIB             June 1999


   [5]  McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
        <a href='#sM.'>M.</a> and S. Waldbusser, &quot;Structure of Management Information
        Version 2 (SMIv2)&quot;, <A HREF="http://RFC.net/std58.html">STD 58</A>, <A HREF="http://RFC.net/rfc2578.html">RFC 2578</A>, April 1999.

   [6]  McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
        <a href='#sM.'>M.</a> and S. Waldbusser, &quot;Textual Conventions for SMIv2&quot;, <A HREF="http://RFC.net/std58.html">STD 58</A>,
        <A HREF="http://RFC.net/rfc2579.html">RFC 2579</A>, April 1999.

   [7]  McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
        <a href='#sM.'>M.</a> and S. Waldbusser, &quot;Conformance Statements for SMIv2&quot;, STD
        58, <A HREF="http://RFC.net/rfc2580.html">RFC 2580</A>, April 1999.

   [8]  Case, J., Fedor, M., Schoffstall, M., and J. Davin, &quot;Simple
        Network Management Protocol&quot;, <A HREF="http://RFC.net/std15.html">STD 15</A>, <A HREF="http://RFC.net/rfc1157.html">RFC 1157</A>, May 1990.

   [9]  Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
        &quot;Introduction to Community-based SNMPv2&quot;, <A HREF="http://RFC.net/rfc1901.html">RFC 1901</A>, January
        1996.

   [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
        &quot;Transport Mappings for Version 2 of the Simple Network
        Management Protocol (SNMPv2)&quot;, <A HREF="http://RFC.net/rfc1906.html">RFC 1906</A>, January 1996.

   [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, &quot;Message
        Processing and Dispatching for the Simple Network Management
        Protocol (SNMP)&quot;, <A HREF="http://RFC.net/rfc2572.html">RFC 2572</A>, April 1999.

   [12] Blumenthal, U., and B. Wijnen, &quot;User-based Security Model for
        Version 3 of the Simple Network Management Protocol (SNMPv3)&quot;,
        <A HREF="http://RFC.net/rfc2574.html">RFC 2574</A>, April 1999.

   [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, &quot;Protocol
        Operations for Version 2 of the Simple Network Management
        Protocol (SNMPv2)&quot;, <A HREF="http://RFC.net/rfc1905.html">RFC 1905</A>, January 1996.

   [14] Levi, D., Meyer, P., and B. Stewart, &quot;SNMP Applications&quot;, RFC
        2573, April 1999.

   [15] Wijnen, B., Presuhn, R., and K. McCloghrie, &quot;View-based Access
        Control Model for the Simple Network Management Protocol
        (SNMP)&quot;, <A HREF="http://RFC.net/rfc2575.html">RFC 2575</A>, April 1999.

   [16] Rigney, C., &quot;RADIUS Accounting&quot;, <A HREF="http://RFC.net/rfc2139.html">RFC 2139</A>, April 1997.








Zorn &amp; Aboba                 Informational                     [Page 12]
<hr><a name='p13'></a>

<A HREF="http://RFC.net/rfc2621.html">RFC 2621</A>              RADIUS Accounting Server MIB             June 1999


<h2><a name='s6.'>6.  Security Considerations</a></h2>

   There are management objects (radiusAccServConfigReset) defined in
   this MIB that have a MAX-ACCESS clause of read-write and/or read-
   create.  Such objects may be considered sensitive or vulnerable in
   some network environments.  The support for SET operations in a non-
   secure environment without proper protection can have a negative
   effect on network operations.

   There are a number of managed objects in this MIB that may contain
   sensitive information. These are:

   radiusAccClientAddress
             This can be used to determine the address of the RADIUS
             accounting client with which the server is communicating.
             This information could be useful in impersonating the
             client.

   radiusAccClientID This can be used to determine the client ID for the
             accounting client with which the server is communicating.
             This information could be useful in impersonating the
             client.

   It is thus important to control even GET access to these objects and
   possibly to even encrypt the values of these object when sending them
   over the network via SNMP.  Not all versions of SNMP provide features
   for such a secure environment.

   SNMPv1 by itself is not a secure environment. Even if the network
   itself is secure (for example by using IPSec), there is no control as
   to who on the secure network is allowed to access and GET/SET
   (read/change/create/delete) the objects in this MIB.

   It is recommended that the implementers consider the security
   features as provided by the SNMPv3 framework. Specifically, the use
   of the User-based Security Model <A HREF="http://RFC.net/rfc2574.html">RFC 2574</A> [12] and the View-based
   Access Control Model <A HREF="http://RFC.net/rfc2575.html">RFC 2575</A> [15] is recommended.  Using these
   security features, customer/users can give access to the objects only
   to those principals (users) that have legitimate rights to GET or SET
   (change/create/delete) them.

<h2><a name='s7.'>7.  Acknowledgments</a></h2>

   The authors acknowledge the contributions of the RADIUS Working Group
   in the development of this MIB.  Thanks to Narendra Gidwani of
   Microsoft, Allan C. Rubens of MERIT, Carl Rigney of Livingston and
   Peter Heitman of American Internet Corporation for useful discussions
   of this problem space.



Zorn &amp; Aboba                 Informational                     [Page 13]
<hr><a name='p14'></a>

<A HREF="http://RFC.net/rfc2621.html">RFC 2621</A>              RADIUS Accounting Server MIB             June 1999


<h2><a name='s8.'>8.  Authors' Addresses</a></h2>

   Bernard Aboba
   Microsoft Corporation
   One Microsoft Way
   Redmond, WA 98052

   Phone: 425-936-6605
   EMail: bernarda@microsoft.com


   Glen Zorn
   Microsoft Corporation
   One Microsoft Way
   Redmond, WA 98052

   Phone: 425-703-1559
   EMail: glennz@microsoft.com

































Zorn &amp; Aboba                 Informational                     [Page 14]
<hr><a name='p15'></a>

<A HREF="http://RFC.net/rfc2621.html">RFC 2621</A>              RADIUS Accounting Server MIB             June 1999


<h2><a name='s9.'>9.  Full Copyright Statement</a></h2>

   Copyright (C) The Internet Society (1999).  All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implmentation may be prepared, copied, published and
   distributed, in whole or in part, without restriction of any kind,
   provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   &quot;AS IS&quot; basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Acknowledgement

   Funding for the RFC Editor function is currently provided by the
   Internet Society.



















Zorn &amp; Aboba                 Informational                     [Page 15]
<hr><a name='p16'></a>

</pre></body></html>
